docs: note investigation order before a direct Fortress ls #35
+14
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ss ls Diagnosing a target's shipped-object shape (e.g. why it landed as many solo tars) should start from the nightly run report, per-target job stdout, and the _vault manifest — hsi ls against tape is a live HPSS call and should be the last-resort confirmation, not the first check. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Jarrod S Doucette (jdoucett)
deleted the
docs/investigate-before-fortress-search
branch
Sign in
to join this conversation on GitHub.
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Documents the investigation order for "what shipped / why did it shard" questions: nightly run report -> per-target job stdout (SIZE-ROUTING COMPLETE) -> _vault/*.manifest.json -> only then a direct
hsi lsagainst Fortress as last-resort confirmation. Prompted by walking through why an X0D baseline archive landed as hundreds of solo tars in florasense-tools.Docs-only change (CLAUDE.md), no code/behavior change.